_tttt_iiii_cccc_llll_tttt_ssss_,,,, _tttt_iiii_cccc_oooo_tttt_ssss_,,,, _tttt_iiii_cccc_oooo_tttt_ssss_oooo_rrrr_dddd - loopback transport providers
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
#include <ticlts.h>
#include <ticots.h>
#include <ticotsord.h>
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
The devices known as _tttt_iiii_cccc_llll_tttt_ssss, _tttt_iiii_cccc_oooo_tttt_ssss, and _tttt_iiii_cccc_oooo_tttt_ssss_oooo_rrrr_dddd are ``loopback
transport providers,'' that is, stand-alone networks at the transport
level. Loopback transport providers are transport providers in every
sense except one: only one host (the local machine) is ``connected to''
a loopback network. Loopback transports present a TPI (_SSSS_TTTT_RRRR_EEEE_AAAA_MMMM_SSSS-level)
interface to application processes and are intended to be accessed via
the TLI (application-level) interface. They are implemented as clone
devices and support address spaces consisting of ``flex-addresses,''
i.e., arbitrary sequences of octets, of length > 0, represented by a
_nnnn_eeee_tttt_bbbb_uuuu_ffff structure.
_tttt_iiii_cccc_llll_tttt_ssss is a datagram-mode transport provider. It offers (connectionless)
service of type _TTTT______CCCC_LLLL_TTTT_SSSS. Its default address size is _TTTT_CCCC_LLLL______DDDD_EEEE_FFFF_AAAA_UUUU_LLLL_TTTT_AAAA_DDDD_DDDD_RRRR_SSSS_ZZZZ.
_tttt_iiii_cccc_llll_tttt_ssss prints the following error messages (see _tttt______rrrr_cccc_vvvv_uuuu_dddd_eeee_rrrr_rrrr(3N)):
_TTTT_CCCC_LLLL______BBBB_AAAA_DDDD_AAAA_DDDD_DDDD_RRRR bad address specification
_TTTT_CCCC_LLLL______BBBB_AAAA_DDDD_OOOO_PPPP_TTTT bad option specification
_TTTT_CCCC_LLLL______PPPP_EEEE_EEEE_RRRR_BBBB_AAAA_DDDD_SSSS_TTTT_AAAA_TTTT_EEEE peer in wrong state
_tttt_iiii_cccc_oooo_tttt_ssss is a virtual circuit-mode transport provider. It offers
(connection-oriented) service of type _TTTT______CCCC_OOOO_TTTT_SSSS. Its default address size
is _TTTT_CCCC_OOOO______DDDD_EEEE_FFFF_AAAA_UUUU_LLLL_TTTT_AAAA_DDDD_DDDD_RRRR_SSSS_ZZZZ. _tttt_iiii_cccc_oooo_tttt_ssss prints the following disconnect messages
(see _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss(3N)):
TCO_NOPEER no listener on destination address
TCO_PEERNOROOMONQ peer has no room on connect queue
_tttt_iiii_cccc_oooo_tttt_ssss_oooo_rrrr_dddd is a virtual circuit-mode transport provider, offering service
of type _TTTT______CCCC_OOOO_TTTT_SSSS______OOOO_RRRR_DDDD (connection-oriented service with orderly release).
Its default address size is _TTTT_CCCC_OOOO_OOOO______DDDD_EEEE_FFFF_AAAA_UUUU_LLLL_TTTT_AAAA_DDDD_DDDD_RRRR_SSSS_ZZZZ. _tttt_iiii_cccc_oooo_tttt_ssss_oooo_rrrr_dddd prints the
following disconnect messages (see _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss(3N)):
TCOO_NOPEER no listener on destination address
TCOO_PEERNOROOMONQ peer has no room on connect queue
Loopback transports support a local IPC mechanism through the TLI
interface. Applications implemented in a transport provider-independent
manner on a client-server model using this IPC are transparently
transportable to networked environments.
Transport provider-independent applications must not include the header
files listed in the synopsis section above. In particular, the options
are (like all transport provider options) provider dependent.
_tttt_iiii_cccc_llll_tttt_ssss and _tttt_iiii_cccc_oooo_tttt_ssss support the same service types (_TTTT______CCCC_LLLL_TTTT_SSSS and _TTTT______CCCC_OOOO_TTTT_SSSS)
supported by the OSI transport-level model. The use of _tttt_iiii_cccc_llll_tttt_ssss and _tttt_iiii_cccc_oooo_tttt_ssss